home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Amiga Plus 2002 #11
/
Amiga Plus CD - 2002 - No. 11.iso
/
Sound
/
BarsnPipes1.16
/
CatalogTranslation
/
readme_translation.doc
< prev
next >
Wrap
Text File
|
2002-10-27
|
6KB
|
184 lines
readme_translation.doc
======================
Here are some important and neccessary informations. I'll write it
so short as possible ...
1. The file for the translation is named : BnP_locale.ct
*.ct means catalog translation
2. The other file is BnP_locale.cd
*.cd means catalog description.
3. For the translation we use the *.ct - file.
4. Use the right version number of the *.ct catalog-file.
If you are not sure, that you use the right version:
- open a CLI-window
- give in : version mypath:BarsnPipes
("mypath:" you must replace with the whole path to
the directory, where your BarnPipes is placed)
- you will get a message like this:
BarsnPipes New 1.03
- the two numers after the point must match the version of
the version in the *.ct catalog-file.
In our example the right *.ct catalog-file version is: 3.0
********************************************************************
The lines in the *.ct - file:
## version $VER: BnP.catalog 1.0 (01.07.01)
the version of this catalog, don't touch this,
otherwise your catalog won't work, the versions
number will increase, also the date
## language X
This line indicates the language of your catalog.
The X must be replaced by the same language-name, like
the system uses in the Locale-Prefs.
(example: italiano or slovensko or ...)
; at the beginning is a comment,
these lines will be ignored by CComp
(the catalog - compiler)
you may write so much comments, like you want
msg_XXX the message identifier
don't touch these lines in ANY way
The empty line below the msg_XXX is the line for your translation.
The original english string is written in the line(s) below as a
comment.
a german (deutsch) example in short:
msg_0 <- the msg_identifier
Typ : <- the translation
; Type: <- the original string
**********************************************************************
extra information:
------------------
1. You will find cases there are more than one commented line
below the translations-line.
example:
msg_224
Bitte geben Sie dem Rhytmus\nZUERST einen Namen !\nWenn Sie ihn für später behalten wollen,\ndann speichern Sie ihn bitte vorher ab.
; Please give\nthe rhythm a name at FIRST !\nIf you want to ke\
; ep it for later:\nSave it please.
You MUST write the translation ALWAYS into ONE line. In the
example above you can see my german translation.
2. You will find "\n" or "|" in some longer strings. These are
separators. After these separators begins a new line.
The "\n" you find in the shortmessage-requesters. Most of these
requesters you quit with an "Okay"-Button.
The "|" you find in the "Are you sure" - messages. So you can
see immediately (during translation) wich kind of (longer)
message this is. In the case of a "Are you sure" continuation
the string starts in lowercase, because "Are you sure" is the
first part of the message .... :-)
In the "Are you sure" continuation you can write up to 5
separators (|). These should be enough, I think.
3. The empty line MUST be filled, otherwise in the running program
the string will be empty.
If you won't make a translation write simply the english string
into this line.
4. I very recommend to save the translation separate (so the original
*.ct will not touched).
See my german translation as an example : BnP_de_locale.ct
5. In some cases you will find a "_" sign in the strings. This indicates
the hotkey, that is filtered out the string by BarsnPipes-program.
That means, you can simple define a hotkey by putting a "_"-sign
BEFORE the char, that shall be the hotkey.
example:
msg_156
; _Phrase Length (in Measures):
Like you can see, the p is the hotkey here. This is CASEINDEPENDENT !
CAUTION:
In the most requesters you can leave with (english) "Cancel" or "Okay".
The Hotkey for these two strings will be used in ALL requesters and are
defined ONLY ONCE!
NEVER use one of these hotkeys for other strings in the requesters.
ALSO don't use the same hotkey twice in one requester.
The best way is, to test all hotkeys after the catalog is compiled.
Compilation:
-----------
If you have translated ALL strings you can start the catalog-compiler,
that comes with this package. I recommend to save the CComp to your C:
directory. So the AMIGA will find it by simply write CComp in the shell.
Open a shell:
1. cd to the directory, where the *.ct and *.cd - files are stored.
Otherwise you must write the whole path to your files.
2. call the compiler:
CComp Catalogdescription/A,Translation/A,Catalog/A
example:
CComp BnP_locale.cd BnP_my_locale.ct BarsnPipes.catalog
This will compile your translation to BarsnPipes.catalog, and saves it
in your current directory. The Name of the *.catalog-file
MUST BE BarsnPipes.catalog. because the BarsnPipes-program search this
so named file.
If compilation is finished, copy the BarsnPipes.catalog to
Locale:catalogs/mylanguage/BarsnPipes.catalog
3. After this all is finished you can start the program BarsnPipes.
I would be very very enjoyed if there are so much as possible translations
could be maked for this fantastic Sequencer program.
The BnP_de_locale.ct is my german translation as an example. Please have
a look at it.
Happy translating .... :-))
Alfred Faust
<alfred.j.faust@gmx.de>